
<html><HEAD>
<LINK REL=STYLESHEET HREF="default.css" TYPE="text/css">
<TITLE>
Target types</TITLE>
</HEAD>
<BODY>

<!-- Header -->
<p class="ancestor" align="right"><A HREF="pbugp9.htm">Previous</A>&nbsp;&nbsp;<A HREF="pbugp11.htm" >Next</A>
<!-- End Header -->
<A NAME="BABHCBDH"></A><h1>Target types</h1>
<A NAME="TI258"></A><p>This section describes each of the targets you can build. </p>
<A NAME="TI259"></A><h2>Application targets</h2>
<A NAME="TI260"></A><p>There are three wizards for creating application targets:<A NAME="TI261"></A>
<ul>
<li class=fi><A HREF="pbugp10.htm#CEGHGICG">Application Target wizard</A></li>
<li class=ds><A HREF="pbugp10.htm#X-REF342889239">Template Application Target
wizard</A></li>
<li class=ds><A HREF="pbugp10.htm#CEGEIHCF">Existing Application Target
wizard</A>
</li>
</ul>
</p>
<A NAME="CEGHGICG"></A><h4>Application Target wizard</h4>
<A NAME="TI262"></A><p>You use the Application Target wizard to create a new PowerScript-based Application
object and the library containing it. You must create any other objects
you need from scratch. </p>
<A NAME="X-REF342889239"></A><h4>Template Application Target
wizard</h4>
<A NAME="TI263"></A><p>You use the Template Application Target wizard to create a
PowerScript-based application, the library containing it, and a
set of basic objects and scripts. If the application requires a
connection to <ACRONYM title = "E A Server" >EAServer</ACRONYM> or
a <ACRONYM title = "sequel" >SQL</ACRONYM> database, the wizard automatically
creates a Connection object.</p>
<A NAME="TI264"></A><p>In the Template Application wizard, you can choose one of
two application types: MDI Application and SDI Application.</p>
<p><b>MDI Application</b>   The wizard automatically generates the shell and scripts for a
basic Multiple Document Interface (MDI) application that includes
these objects:<A NAME="TI265"></A>
<ul>
<li class=fi>Application
object</li>
<li class=ds>Frame window</li>
<li class=ds>Frame menu</li>
<li class=ds>Base sheet window</li>
<li class=ds>Sheet menu</li>
<li class=ds>Sheet menu service object</li>
<li class=ds>Sheet windows</li>
<li class=ds>About window</li>
<li class=ds>Toolbar window</li>
<li class=ds>Connection service object (if database connection
is needed)</li>
<li class=ds>Project object (optional; can build later using
a Project wizard)
</li>
</ul>
</p>
<A NAME="TI266"></A><p>You can run the MDI application immediately by clicking the
Run button on the PowerBar. You can open sheets, display an About
box, and select items from menus. The To-Do List can help you use
the application as a starting point for continuing development of
an MDI application. </p>
<p><b>SDI Application</b>   In the Template Application wizard, you can also choose to create
a Single Document Interface (SDI) application. An SDI application
has only one main window with a menu and an about window. If the
application requires a connection to <ACRONYM title = "E A Server" >EAServer</ACRONYM> or
a <ACRONYM title = "sequel" >SQL</ACRONYM> database, the wizard automatically creates
a Connection object.</p>
<A NAME="TI267"></A><p>For information about building MDI and SDI
applications, see <i>Application Techniques</i>
. </p>
<A NAME="CEGEIHCF"></A><h4>Existing Application Target
wizard</h4>
<A NAME="TI268"></A><p>You use the Existing Application Target wizard to add a target
to your workspace that uses an application you built in an earlier
version of PowerBuilder. After
you complete the wizard, the Migrate Application dialog box opens
so you can migrate the application to this version. </p>
<p><b>Before you migrate</b>   Always make a backup copy of all the <ACRONYM title = "pibbles" >PBLs</ACRONYM> used
in an application before you migrate it to a new version of PowerBuilder.</p>
<A NAME="TI269"></A><p>You can use the Migration Assistant to check for obsolete
syntax in your application before you migrate; then you can make
changes in the earlier version of PowerBuilder and avoid some migration
errors. The Migration Assistant is particularly useful if you are
migrating from PowerBuilder 6 or earlier. Open the Migration Assistant
from the Tool tab of the New dialog box, and press F1 if you need
Help in the wizard.</p>
<A NAME="TI270"></A><p>You should also check the release notes for the version of
PowerBuilder that you are using to find out if there are any migration
issues that might affect you.</p>
<A NAME="TI271"></A><p>For more information about migrating targets, see <A HREF="pbugp60.htm#BGBJHCBC">"Migrating targets"</A>.</p>
<A NAME="TI272"></A><p>For information about building standard PowerBuilder
applications, see the rest of this book and <i>Application
Techniques</i>
. </p>
<A NAME="TI273"></A><h2>Component targets</h2>
<A NAME="TI274"></A><h4><ACRONYM title = "E A Server" >EAServer</ACRONYM> Component Target
wizard</h4>
<A NAME="TI275"></A><p>You use the <ACRONYM title = "E A Server" >EAServer</ACRONYM> Component
Target wizard to create a new target containing a custom class user
object (to which you later add methods and properties) with the
characteristics required by an <ACRONYM title = "E A Server" >EAServer</ACRONYM> component
object that you can deploy to <ACRONYM title = "E A Server" >EAServer</ACRONYM>.
If you want to create an <ACRONYM title = "E A Server" >EAServer</ACRONYM> component in
an existing EAServer component target, use the wizard on the PB
Object page.</p>
<A NAME="TI276"></A><p>Access to the <ACRONYM title = "E A Server" >EAServer</ACRONYM> component
from a PowerBuilder client application is gained through a Proxy
object. You create a Proxy object using the <ACRONYM title = "E A Server" >EAServer</ACRONYM> Proxy wizard on the
Project tab page.</p>
<A NAME="TI277"></A><h4>Application Server Component Target wizard</h4>
<A NAME="TI278"></A><p>You use the Application Server Component Target wizard to
create a new target containing a custom class user object (to which
you later add methods and properties) with the characteristics required
by an Application Server component object that you can deploy to
a J2EE-compliant application server. To deploy
the component to the application server, you must have the PowerBuilder
Application Server Plug-in, which is a separate Sybase product.</p>
<A NAME="TI279"></A><p>If you want to create an application server component in an
existing application server target, use the wizard on the PB Object
page.</p>
<A NAME="TI280"></A><p>Access to the application server component from a PowerBuilder
client application is gained through a Proxy object. You create
a Proxy object using the Application Server Proxy wizard on the
Project tab page.</p>
<A NAME="TI281"></A><h2>.NET targets</h2>
<A NAME="TI282"></A><h4>.NET Web Forms Application wizard</h4>
<A NAME="TI283"></A><p>The .NET Web Forms Application wizard eases the task of deploying
new or existing PowerBuilder client-server applications
to the Web and allows you to use your PowerBuilder skills to create
new Web applications that use ASP.NET technology. </p>
<A NAME="TI284"></A><h4>.NET Windows Forms Application wizard</h4>
<A NAME="TI285"></A><p>The .NET Windows Forms Application wizard builds a target
that deploys a PowerBuilder application as a .NET Windows Forms
application. Applications that have a rich user interface that relies
on resources available on the client computer, such as a complex
MDI design, graphics, or animations, or that perform intensive data
entry or require a rapid response time, make good candidates for
deployment as PowerBuilder .NET Windows Forms applications. </p>
<A NAME="TI286"></A><p>One of the choices you can make in the wizard is whether the
application will be deployed as a smart client application. A smart
client application can work either online (connected to distributed
resources) or offline, and can take advantage of "intelligent
update" technology for deployment and maintenance. </p>
<A NAME="TI287"></A><h4>.NET Web Service and .NET Assembly wizards</h4>
<A NAME="TI288"></A><p>The PowerBuilder .NET Web Service and .NET Assembly wizards
build targets that deploy PowerBuilder custom class user objects
as .NET Web services or assemblies.</p>
<A NAME="TI289"></A><p>For more information about .NET targets, see<i> Deploying
Applications and Components to .NET</i>
.</p>

